home *** CD-ROM | disk | FTP | other *** search
- Path: news1.h1.usa.pipeline.com!usenet
- From: grantp@usa.pipeline.com(Pete)
- Newsgroups: comp.lang.c++
- Subject: Re: bc4.0, Windows, Cursor
- Date: 20 Jan 1996 11:12:52 GMT
- Organization: Kalevi, Inc.
- Message-ID: <4dqink$sge@news1.usa.pipeline.com>
- References: <4dpiba$gij@oxy.rust.net>
- NNTP-Posting-Host: pipe7.h1.usa.pipeline.com
- X-PipeUser: grantp
- X-PipeHub: usa.pipeline.com
- X-PipeGCOS: (Pete)
- X-Newsreader: Pipeline USA v3.3.0
-
- On Jan 20, 1996 05:00:33 in article <Re: bc4.0, Windows, Cursor>,
- 'ebennett@rust.net' wrote:
-
-
- >slane@interlink.net (Simon Lane) wrote:
- >
- >>Using SetCursor() to change the cursor from IDC_ARROW to IDC_WAIT works
- >>until the user actually moves the cursor. How do you change the cursor
- >>for the entire desktop, or at the least for the current active window
- >>and make sure that it does not change back ?
- >
- >>Thanks in advance, slane@interlink.net
- >
- >Process the WM_MOUSEMOVE message and call SetCursor() every time you
- >receive that message.
- >
- Another (and often a better) way is to capture the mouse,
- something like:
-
- WARNING Untested code using WinAPI -- OWL and MFC have
- equivalent methods.
-
- ::SetCursor(hWnd, IDC_WAIT);
- ::SetCapture(hWnd);
- ..... do your stufffff
- ::ReleaseCapture();
-
-
- Of course, ReleaseCapture can be in a message response function
- so that you can process other windows messages while the
- hourglass remains in effect.
-
- --
- Pete Grant
- Kalevi, Inc.
- Object Oriented Software Development
-